System and computer program product for synchronizing direct access storage volumes

ABSTRACT

A system and computer program product for synchronizing direct access storage volumes designated as managed by storage management software with direct access storage volumes available to a computer system. An identifier of a volume is provided. The volume is connected to and available to a computer system, and is not managed by storage management software. The identifier is matched with an identification pattern included in a record of a database accessible to the computer system. Management options that facilitate managing the volume by the storage management software, and that are included in the record are retrieved from the record. The volume is automatically added to a set of volumes being managed by the storage management software. The adding of the volume includes designating the volume as being managed by the storage management software and providing the management options to the storage management software.

This application is a continuation application claiming priority to Ser.No. 11/270,763, filed Nov. 8, 2005.

BACKGROUND OF THE INVENTION

1. Technical Field

The present invention relates to a method and system for synchronizingdirect access storage volumes, and more particularly to a technique forsynchronizing direct access storage volumes managed by storagemanagement software with direct access storage volumes available to acomputer system.

2. Related Art

When adding or removing direct access storage volumes on a computingsystem, storage management software needs to be manually notified of thevolume(s) being added or removed. Since the additions or removals aremanually performed, human error (e.g., oversight or lack of knowledge)can result in the following problems: (1) failing to add the volume; (2)incorrectly adding the volume; and (3) failing to remove the volume fromthe storage management software. These problems cause a lack ofsynchronization between the volumes recognized by the storage managementsoftware and the volumes available to the system, thereby leading todifficulties in capacity management, backups, and the processing ofvolumes by the storage management software. For example, failing to addor incorrectly adding the volume can result in data not being expired ormoved elsewhere due to a lack of use, thereby causing a volume to runout of space. Thus, there exists a need for an improved technique foradding volumes to and removing volumes from storage management software.

SUMMARY OF THE INVENTION

In first embodiments, the present invention provides a method ofsynchronizing direct access storage volumes managed by storagemanagement software with direct access storage volumes available to acomputer system, comprising:

identifying a first set of one or more direct access storage volumes,the first set physically connected to and available to the computersystem, the identifying providing an identifier of a direct accessstorage volume of the first set;

matching the identifier with an identification pattern included in arecord of one or more records residing in a database accessible by thecomputer system, the identification pattern identifying the directaccess storage volume directly or a group of direct access storagevolumes including the direct access storage volume;

responsive to the matching, retrieving from the record a plurality ofmanagement options capable of facilitating a management of the directaccess storage volume by the storage management software, wherein thedirect access storage volume is not designated as being managed by thestorage management software; and

automatically adding the direct access storage volume to a second set ofone or more direct access storage volumes, the second set designated asbeing managed by the storage management software,

wherein the adding comprises:

-   -   designating the direct access storage volume as being managed by        the storage management software, and    -   providing the plurality of management options to the storage        management software, wherein the storage management software        associates the plurality of management options with the direct        access storage volume.

In second embodiments, the present invention provides a system forsynchronizing direct access storage volumes managed by storagemanagement software with direct access storage volumes available to acomputer system, comprising:

means for identifying a first set of one or more direct access storagevolumes, the first set physically connected to and available to thecomputer system, the identifying providing an identifier of a directaccess storage volume of the first set;

means for matching the identifier with an identification patternincluded in a record of one or more records residing in a databaseaccessible by the computer system, the identification patternidentifying the direct access storage volume directly or a group ofdirect access storage volumes including the direct access storagevolume;

means for retrieving from the record, responsive to the matching, aplurality of management options capable of facilitating a management ofthe direct access storage volume by the storage management software,wherein the direct access storage volume is not designated as beingmanaged by the storage management software; and

means for automatically adding the direct access storage volume to asecond set of one or more direct access storage volumes, the second setdesignated as being managed by the storage management software,

wherein the means for adding comprises:

-   -   means for designating the direct access storage volume as being        managed by the storage management software, and    -   means for providing the plurality of management options to the        storage management software, wherein the storage management        software associates the plurality of management options with the        direct access storage volume.

In third embodiments, the present invention provides a computer programproduct comprising a computer-usable medium including computer-usableprogram code for synchronizing direct access storage volumes managed bystorage management software with direct access storage volumes availableto a computer system, the computer program product including:

computer-usable code for identifying a first set of one or more directaccess storage volumes, the first set physically connected to andavailable to the computer system, the identifying providing anidentifier of a direct access storage volume of the first set;

computer-usable code for matching the identifier with an identificationpattern included in a record of one or more records residing in adatabase accessible by the computer system, the identification patternidentifying the direct access storage volume directly or a group ofdirect access storage volumes including the direct access storagevolume;

computer-usable code for retrieving from the record, responsive to thematching, a plurality of management options capable of facilitating amanagement of the direct access storage volume by the storage managementsoftware, wherein the direct access storage volume is not designated asbeing managed by the storage management software; and

computer-usable code for automatically adding the direct access storagevolume to a second set of one or more direct access storage volumes, thesecond set designated as being managed by the storage managementsoftware,

wherein the computer-usable code for adding comprises:

-   -   computer-usable code for designating the direct access storage        volume as being managed by the storage management software, and    -   computer-usable code for providing the plurality of management        options to the storage management software, wherein the storage        management software associates the plurality of management        options with the direct access storage volume.

In fourth embodiments, the present invention provides a method fordeploying computing infrastructure, comprising integratingcomputer-readable code into a computing system, wherein the code incombination with the computing system is capable of performing a processof synchronizing direct access storage volumes managed by storagemanagement software with direct access storage volumes available to acomputer system, the process comprising:

identifying a first set of one or more direct access storage volumes,the first set physically connected to and available to the computersystem, the identifying providing an identifier of a direct accessstorage volume of the first set;

matching the identifier with an identification pattern included in arecord of one or more records residing in a database accessible by thecomputer system, the identification pattern identifying the directaccess storage volume directly or a group of direct access storagevolumes including the direct access storage volume;

responsive to the matching, retrieving from the record a plurality ofmanagement options capable of facilitating a management of the directaccess storage volume by the storage management software, wherein thedirect access storage volume is not designated as being managed by thestorage management software; and

automatically adding the direct access storage volume to a second set ofone or more direct access storage volumes, the second set designated asbeing managed by the storage management software,

wherein the adding comprises:

-   -   designating the direct access storage volume as being managed by        the storage management software, and    -   providing the plurality of management options to the storage        management software, wherein the storage management software        associates the plurality of management options with the direct        access storage volume.

Advantageously, the technique described by the present inventionprovides an automatic process that avoids the manual addition or manualremoval of volumes recognized by storage management software in responseto a volume being added or removed from the system. Further, the presentinvention provides an automatic method for updating a volume recognizedby storage management software in response to management optionsassociated with the volume being updated. Changes to management optionsof a group of volumes can be performed in a single step. Moreover, acontrol file can be generated to include system-specific identifiers,which allows the same control file to be used across multiple systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a prior art system which requires a manualupdate of management options of volumes managed by storage managementsoftware, a manual addition of volumes that are to be managed by storagemanagement software, and a manual removal of volumes from being managedby storage management software.

FIG. 2 is a block diagram of a system for synchronizing volumes managedby storage management software with volumes available to a computingsystem, in accordance with embodiments of the present invention.

FIG. 3 depicts a flow chart of a process for synchronizing volumesmanaged by storage management software with volumes available to acomputing system, and which is implemented in the system of FIG. 2, inaccordance with embodiments of the present invention.

FIG. 4A is a flow chart of a process for retrieving volume managementoptions for the process of FIG. 3 by searching a control file by a firstfit approach, in accordance with embodiments of the present invention.

FIG. 4B is a flow chart of a process for retrieving volume managementoptions for the process of FIG. 3 by searching a control file by a bestfit approach, in accordance with embodiments of the present invention.

FIG. 5 is a block diagram of a computing system included in the systemof FIG. 2, in accordance with embodiments of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a block diagram of a prior art system which requires a manualupdate of management options of volumes managed by storage managementsoftware, a manual addition of volumes that are to be managed by storagemanagement software, and a manual removal of volumes from being managedby storage management software. System 100 includes a computing system102 physically connected to three groups of volumes 104, 106, and 108(e.g., groups of hard drives). A fourth group of volumes 110 is removedfrom computing system 102, but was previously connected thereto. Volumegroup 104 is managed by management software such as System ManagedStorage (SMS) 112, a software facility that automates and centralizesthe management of data security, placement, migration, backup, recall,recovery and deletion to ensure that current data is available whenneeded, and obsolete data is removed from storage. SMS 112 utilizesHierarchical Storage Manager (HSM) 114 to carry out volume managementtasks that include the placement, backup and expiration of data, and theautomation of these tasks.

Volume group 106 is managed directly by HSM 114. HSM 114 has knowledgeof (i.e., has access to) sets of management options, where each set isassociated with one of the volumes that HSM manages. Management optionsare characteristics or attributes that are defined to facilitate themanagement of a volume. In the configuration of FIG. 1, the datamanagement needs associated with the volumes of volume group 106 havebeen updated, thereby requiring an update of management options known toHSM 114 and associated with the volumes of group 106.

Volume group 108 includes volumes that are physically connected tocomputing system 102 (e.g., volumes that have been recently connected tocomputing system 102). The volumes of volume group 108 are unknown to(i.e., not designated as being managed by) HSM 114, are not managed bySMS 112, and need to be added to the set of volumes managed by HSM 114.

Volume group 110 includes volumes that are removed from (i.e., notconnected to) computing system 102 (e.g., volumes that had beenphysically connected to computing system 102, but which were recentlydisconnected from computing system 102). As the volumes of volume group110 are currently known to (i.e., designated as being managed by) HSM114, removal of these volumes from the set of volumes managed by HSM 114is required.

In conventional systems, the aforementioned updating of managementoptions associated with volume group 106, adding volume group 108 to theset of volumes managed by HSM 114, and removing volume group 110 fromthe set of volumes managed by HSM 114 are not automated and requiremanual actions.

The present invention automates the process of updating managementoptions, adding volumes to management software and removing volumes frommanagement software so that the configuration shown in FIG. 1 canautomatically and dynamically become the configuration shown in FIG. 2.

FIG. 2 is a block diagram of a system for synchronizing volumes managedby storage management software with volumes available to a computingsystem, in accordance with embodiments of the present invention. FIG. 2depicts a system 200 that includes a computing system 202 (e.g., a z/OSmainframe system available from International Business MachinesCorporation of Armonk, N.Y.) physically connected to volume groups 204,206 and 208. As used herein, a volume (a.k.a. direct access storagevolume) is defined to be a data storage device in a computingenvironment for which a backup is performed. In the preferredembodiment, a volume is a hard drive or a direct access storage device(DASD). As used herein, a volume that is available is available tocomputing system 202 for storage and/or management of data, and isdefined to be a volume physically connected to computing system 202.

Volume group 204 includes volumes managed by SMS 212 and known to (e.g.,indirectly managed by) HSM 214 via SMS 212. Volume group 206 includesvolumes that are not managed by SMS 212, are currently managed by HSM214, and have had one or more of their associated management optionsupdated. Volume group 208 includes volumes that are physically connectedto and available to computing system 202, are not managed by SMS 212,and have been added to the set of volumes managed by HSM 214. In oneexample, volumes in groups 206 and 208 are appropriately managed by HSM214 and cannot be appropriately managed by SMS 212 because HSM 214operates at a volume level, treating all data on a single volume in thesame manner, while SMS 212 operates at a file level. Volume group 210includes volumes that are not connected (i.e., are removed) fromcomputing system 202, and are not managed by SMS 212 or HSM 214. Forexample, volumes in group 210 have been removed from computing system202 since the most recent backup of volumes connected to computingsystem 202.

SMS 212 and HSM 214 have capabilities as described above relative to SMS112 and HSM 114, respectively. SMS 212 sets management optionsassociated with individual volumes, and requests volume management workor information from HSM 214. HSM 214 stores volume managementinformation relative to the management options set by SMS 212. AlthoughSMS 212 and HSM 214 are shown in the FIG. 2 configuration as beingoutside computing system 202, both SMS 212 and HSM 214 reside withincomputing system 202. As examples, SMS 212 is the Data Facility SystemManaged Storage (DFSMS®) and HSM 214 is the Data Facility System ManagedStorage Hierarchical Storage Manager (DFSMShsm), which are bothavailable from International Business Machines Corporation. The presentinvention contemplates that the HSM component of FIG. 2 can be anystorage management software that has the aforementioned capabilities ofHSM 214.

A control file 216 is a database including a plurality of records. Eachrecord of control file 216 includes a unique identifier (a.k.a.identification pattern) that identifies a specific volume or a group ofvolumes capable of being available to (i.e., physically connected to)computing system 202. For example, control file 216 includessix-character volume serial numbers (a.k.a. volsers) identifying eachhard drive or DASD available to computing system 202. As anotherexample, control file 216 includes volume serial number masks thatidentify groups of volumes that can be available to computing system202. Each record of control file 216 also includes a set of managementoptions (e.g., HSM management details). Each set of management optionsis associated with an identification pattern of the control file, andprovides information regarding the management of data on a volumeidentified by the associated identification pattern. Examples ofmanagement of data include the backup of a volume, deletion of avolume's data if the data is expired, and migration of data from onevolume to another storage device (e.g., a tape storage device). In oneembodiment, control file 216 resides within computing system 202,although this arrangement is not shown in FIG. 2. Data in control file216 is initially input and updated manually.

A delta list 218 is a list comparing a first set of one or more volumesthat are known to HSM 214 to a second set of one or more volumesavailable to computing system 202. As used herein, a volume known to HSM214 is defined as a volume directly or indirectly managed or controlledby HSM 214. Delta list 218 indicates whether or not the first set ofvolumes matches the second set of volumes. The first set of volumesmatches the second set if the first set and second set volumes areassociated in a one-to-one correspondence and the corresponding volumesare identical (e.g., based on matching volume identifiers), and for eachvolume in the first set, management options associated a volume of thefirst set matches management options associated with its correspondingvolume in the second set. If the corresponding volumes are notidentical, or if the management options of corresponding volumes are notidentical, then the first set does not match the second set. When thedelta list indicates that the first set does not match the second set,the present invention provides a technique for automaticallysynchronizing the first and second sets of volumes (i.e., automaticallycreating a match between the first set of volumes and second set ofvolumes).

Via the volume identification information from control file 216, deltalist 218 indicates that volume groups 204, 206 and 208 are available tocomputing system 202, and that volume group 210 is not available tocomputing system 202. Further, the identifiers and management optionsfrom control file 216, and the volumes and associated management optionsknown to HSM 214 are utilized so that delta list 218 indicates volumesfor which synchronization is required.

Delta list 218 indicates that volume group 204 is available to computingsystem 202 and is known to HSM 214, with no changes having been made tothe management options. The remaining sections of delta list 218indicate that a previous configuration of volume groups (i.e., similarto the configuration shown in FIG. 1) lacked synchronization relative tovolume groups 206, 208 and 210, and also indicate the changes to theprevious configuration that have been automatically performed togenerate the configuration shown in FIG. 2, which depicts asynchronization between the volumes available to computing system 202and the volumes known to HSM 214.

For volume group 206, delta list 218 indicates that management optionsin control file 216 had been updated, causing a mismatch when thosecontrol file management options are compared to the management optionsknown to HSM 214. A synchronization process disclosed by the presentinvention automatically applied changes to the management options knownto HSM 214 so that they match the updated control file managementoptions for volume group 206.

Further, delta list 218 indicates that volume group 208 had beenpreviously unknown to HSM 214. The synchronization process automaticallyadded the volumes of volume group 208 to the set of volumes managed byHSM 214.

Still further, delta list 218 indicates that volume group 210 had beenpreviously known to HSM 214, but is currently not available to computingsystem 202. The synchronization process automatically removes thevolumes of volume group 210 from HSM 214. That is, the volumes in group210 are removed from the set of volumes being managed by HSM 214.

A software-based volume synchronization system (shown in FIG. 5, but notshown in FIG. 2) residing in computing system 202 interacts with HSM 214and control file 216 to collect the volume identification and managementoptions from HSM 214 and control file 216, and performs theaforementioned synchronization process that includes the volumeadditions, updates and removals indicated by delta list 218. Thesynchronization process performed by the volume synchronization system,and which is utilized to generate the configuration shown in FIG. 2 isdescribed below relative to FIG. 3.

Although FIG. 2 includes HSM 214 and SMS 212, other storage managementsoftware that is capable of managing volumes can take the place of HSM214 and/or SMS 212, while still providing the capabilities and featuresof the present invention. For example, Fast Dump Restore (FDR®) is asoftware product providing DASD management that may be employed insteadof HSM 214. FDR® management software is available from Innovation® DataProcessing of Little Falls, N.J.

FIG. 3 depicts a flow chart of a process for synchronizing volumesmanaged by storage management software with volumes available to acomputing system, and which is implemented in the system of FIG. 2, inaccordance with embodiments of the present invention. The volumesynchronization process of FIG. 3 begins at step 300. At step 302, alist of volumes available to (i.e., physically connected to) the systemis generated by a data collection software-based tool such as DCOLLECT.DCOLLECT is a data collection facility that obtains a list of volumesavailable to a computer system, as well as other information related tospace utilization and capacity planning. DCOLLECT is provided by IDCAccess Method Services (IDCAMS), which is a data management utility forz/OS mainframes, and is available from International Business MachinesCorporation of Armonk, N.Y. The list generated in step 302 ishereinafter referred to as the system list. Step 302 also obtainsidentification data (e.g., a serial number) that identifies each volumein the system list. For example, step 302 obtains one or more uniquevolume serial numbers associated with the one or more direct accessvolumes identified by DCOLLECT in a one-to-one correspondence. It willbe apparent to one skilled in the art that software tools or methodsother than DCOLLECT are available to produce the system list.

A loop begins at step 304 for the first volume in the system list, andthe first iteration of the loop includes a search of control file 216(see FIG. 2) for a record that includes an identifier that matches thevolume identification data (e.g., volume serial number) collected instep 302 for the first volume of the system list. For a subsequentiteration of the loop starting at step 304, the next volume in thesystem list becomes the current volume, and another search of controlfile 216 (see FIG. 2) is performed to find volume identification thatmatches the current volume. As used herein relative to the loop startingat step 304, the current volume is defines as the volume included in thesystem list for which the control file is being searched to find anidentifier matching the volume identification data associated with thevolume. For example, the current volume's serial number obtained byDCOLLECT is used to match a specific serial number or a generic serialnumber pattern or mask in control file 216 (see FIG. 2). A serial numbermask in control file 216 (see FIG. 2) can be, for instance, “M..SH.”where the periods indicate character positions in which any charactercan appear. In this example, any six-character volume serial number thathas M, S and H in the first, fourth and fifth character positions,respectively, and any character in the second, third and sixth characterpositions (e.g., MABSH1) is considered a match to the M..SH. mask.Hereinafter, a match between the volume identification data of thecurrent volume as determined by step 302 and an identifier in a recordof control file 216 (see FIG. 1) is simply referred to as a matchbetween the current volume and the control file record. Specifictechniques for determining the match in step 304 are discussed belowrelative to FIGS. 4A and 4B.

In response to finding a match between the current volume and a recordof control file 216 (see FIG. 2), step 304 also retrieves the managementoptions in the matching record of control file 216 (see FIG. 2). Thevolume management options retrieved by step 304 include, for example,the type of the volume (e.g., primary or migration) and managementattributes related to the type of volume. In one embodiment, each recordof control file 216 (see FIG. 2) includes a volume serial number mask inpredefined columns of a text file, and indicators of management optionsin other predefined columns. For example, a control file can include thefollowing records:

M . . S H. P Y Y T 80 70 WEEKLY M . . S Y. P Y T 80 70 WEEKLY . . . . .. . . . P Y WEEKLY

The sample control file above indicates volume serial number masks inthe leftmost 6 columns (e.g., M..SH.), where the period is a symbol thatcan be matched with any character. Following each mask is the characterP in a predefined column that indicates the type of a volume that ismatched to the mask. In this case, P indicates that the volume is aprimary volume. A primary volume is a hard disk or direct access storagedevice that is available to users for data storage and datamanipulation. Other characters replacing P in the predefined column candesignate other volume types. For example, M indicates a migrationvolume, which is a volume to which unused data is moved from a primaryvolume to make space for high-availability data on the primary volume.

In each of the sample records above, the characters to the right of thevolume type character (e.g., P) indicate volume management optionsassociated with the record's designated volume type. Since P is thevolume type in the control file example shown above, the remainingcharacters in each record indicate management options associated with aprimary volume. A character or string of characters and its columnposition(s) determine a particular management option according topredefined descriptions that are associated with one or more columns. Inone embodiment, control file 216 (see FIG. 2) includes commented linesthat describe the management options and indicate the column(s)associated with each management option.

As one example, primary volume management options retrieved by step 304are related to an automatic backup of data on the volume during aspecified cycle and to a specified category of a backup device, and inresponse to the data being at least a specified age, or a specified timeelapsing since the most recent reference of the data; an automatic fullvolume dump of all allocated space on the primary volume to a designatedtape dump volume based on a specified frequency; an automatic migrationof data from the primary volume to a migration volume in response to aspecified threshold level of occupancy being exceeded, the data being atleast a specified age, or a specified time elapsing since the mostrecent reference of the data; and an automatic recall of data from amigration volume to the primary volume.

In the sample control file shown above, the first Y character of thefirst record indicates that an automatic dump feature has beenactivated; the second Y character indicates that an automatic backupfeature has been activated; the T character indicates that tape, ratherthan a direct access storage device (DASD), is designated as the type ofbackup device; 80 is the high threshold percentage for incrementalmigration; 70 is the low threshold percentage for daily migration; andWEEKLY is the name of a dumpclass in HSM 214 (see FIG. 2).

During daily migration, if the occupancy rate of the primary volumeassociated with the record exceeds the low threshold, data on the volumeis migrated to another volume until the occupancy rate is below the lowthreshold. Nothing else can be done by the volume until its rate is lessthan the low threshold. During incremental migration (e.g., occurs everyhour), if the occupancy rate of the primary volume exceeds the highthreshold, data on the volume is migrated to another volume until therate is below the high threshold. Incremental migration is not appliedto every volume, but rather to only a specified group of volumes. Acustomization of HSM 214 (see FIG. 2) can provide an automated migrationfeature by which migration automatically starts in response to passing alow or high threshold.

The WEEKLY dumpclass included in the first record shown above indicatesthat the class will not dump the primary volume associated with therecord within 7 days of its last dump. Time periods other than 7 dayscan be indicated by other dumpclasses (e.g., MONTHLY). Dumpclasses aredefined by an administrator and can have any name up to a maximum numberof characters (e.g., 8 characters). HSM 214 (see FIG. 2) does not defineany dumpclasses by default. A volume may have more than one dumpclassassociated therewith, such as both WEEKLY and MONTHLY.

Other characters or character strings can be included and/or othercolumns can be utilized in a control file record to indicate othermanagement options (e.g., activation of an automatic migration feature,activation of an automatic recall feature, deletion of the volume basedon age or backup status, etc.).

In one embodiment, a catchall serial number mask (e.g., “ . . . ” in thesample control file shown above) is placed in the last record of thecontrol file, where the last record also includes a predefined set ofminimum management options that are to be associated with any volumethat does not conform to the volume identification or volume namingstandard that is incorporated into the other records of the control file(e.g., via the volume serial number masks). In the control file exampleshown above, any volume serial number that does not match one of themasks listed prior to the last mask is automatically matched to the . .. mask, which designates the volume as a primary volume with theautomatic dump feature activated.

Inquiry step 306 queries HSM 214 (see FIG. 2) to determine if thecurrent volume is known to (i.e., managed by or controlled by) HSM 214(see FIG. 2). For instance, the current volume is known to HSM 214 (seeFIG. 2) if the volume identification data associated with the currentvolume, which is collected by step 302, matches one of the volumeidentifiers known by HSM 214 (see FIG. 2), which identify the volumesmanaged by HSM 214 (see FIG. 2). If step 306 determines that the currentvolume is not managed by HSM 214 (see FIG. 2), then step 308automatically adds the current volume to a set of one or more volumesmanaged by HSM 214 (see FIG. 2). The management options retrieved instep 304 which are associated with the current volume are also added toHSM 214 (see FIG. 2) in step 308. The addition of the current volume andmanagement options in step 308 can be performed by, for example, acommand line interface (CLI) or an application programming interface(API). Adding a volume to a set of one or more volumes designated asbeing managed by HSM 214 (see FIG. 2) is defined as designating thevolume as being managed by HSM 214 (see FIG. 2) and providing themanagement options associated with the volume to HSM 214 (see FIG. 2),wherein the HSM associates the management options with the volume.Hereinafter, adding a volume to a set of one or more volumes designatedas being managed by HSM 214 (see FIG. 2) is also referred to simply asadding the volume to HSM 214 (see FIG. 2).

Returning to inquiry 306, if the current volume is being managed by HSM214 (see FIG. 2), then step 311 queries HSM 214 to retrieve previouslygenerated management options which HSM 214 has knowledge of andassociates with the current volume. Inquiry step 312 compares the volumemanagement options retrieved in step 304 to the management optionsretrieved in step 311. If the comparison in step 312 determines that themanagement options of the current volume have changed since thegeneration of the management options currently known to HSM 214 (seeFIG. 2), then step 314 automatically updates the current volume'smanagement options in HSM 214 (see FIG. 2) to match (i.e., to beidentical to) the management options retrieved in step 304. The step 314update is performed by, for instance, a CLI or an API. On the otherhand, if step 312 determines that the management options of the currentvolume have not changed, then no update action is required, as isindicated by step 316.

Following steps 308, 314 and 316, inquiry step 310 determines if thesystem list includes at least one volume for which an identifier andmanagement options have not been found by step 304. If step 310determines that a system list volume remains whose identifier has notyet been searched for in step 304, the process of FIG. 3 loops back tostep 304, with the next volume in the system list becoming the currentvolume. If inquiry step 310 determines that all volumes in the systemlist have been utilized in the iterations of the loop beginning at step304, then the synchronization process continues with volume removal atstep 318. Step 318 generates a list that identifies the volumes that aredesignated as being managed by (i.e., known to) HSM 214 (see FIG. 2).Hereinafter, the list generated in step 318 is referred to as themanagement software list.

A condition-controlled loop begins at step 320 for the first volume inthe management software list, and the first iteration of the loopincludes inquiry step 320 that searches the system list generated instep 302 for the first volume of the management software list. Forexample, inquiry 320 searches the system list for an identifier thatidentifies the first volume in the management software list (i.e., anidentifier that matches an identifier associated with the first volumeby the management software). In the first iteration of the step 320loop, the first volume in the management software list is the currentvolume. For a subsequent iteration of the loop starting at step 320, thenext volume of the management software list becomes the current volume,and another search of the system list is performed to determine whetherthe current volume is in the system list. As used herein relative to theloop starting at step 320, the current volume is defined as the volumeincluded in the management software list for which the system list isbeing searched to find an identifier that matches the identifierassociated with the volume by the management software.

If inquiry step 320 determines that the current volume in the managementsoftware list is not also in the system list, then step 322automatically removes the current volume from the management softwarelist by, for example, a CLI or an API. Removal from the managementsoftware list indicates that the removed volume is no longer managed byHSM 214 (see FIG. 2). If inquiry 320 determines that the current volumein the management software list is also in the system list, then inquiry324 determines if one or more volumes remain in the management softwarelist that have yet to be compared to the system list in step 320. Ifstep 324 determines that at least one volume has yet to be compared instep 320, then the process of FIG. 3 repeats starting at inquiry step320, with the next volume in the software management list becoming thecurrent volume. If step 324 determines that no other volumes remain inthe management software list that have not been compared to the systemlist in step 320, then the synchronization process ends at step 326.

It will be apparent to one skilled in the art that the REXX codeincluded in the Code Example section presented below can be utilized toimplement steps 308, 314 and 322 of the synchronization process of FIG.3.

The synchronization process of FIG. 3 is, for instance, efficientlyutilized in conjunction with, and prior to, a backup or dump ofcomputing system 202, or a restart of the management software. Forinstance, backups of computing system 202 are scheduled nightly, and avolume is added to computing system 202 during the day. Instead ofrunning the synchronization process during the day, immediately afterthe volume is added, the synchronization process is executed at night intandem with the nightly backup. First the synchronization processexecutes to add the volume to the set of volumes managed by themanagement software, and then the scheduled backup executes.

In one embodiment, the determinations made in the inquiry steps 306, 312and 320 generate delta list 218 (see FIG. 2), which includes a list ofdifferences between the set of volumes available to system 202 (see FIG.2) and the set of volumes designated as being managed by HSM 214 (seeFIG. 2).

In another embodiment that utilizes a single command that is capable ofperforming both the adding of the volume in step 308 and the updating ofmanagement options in step 314, the steps of 306, 308, 311, 312, 314 and316 can be replaced by a new step 305 (not shown). In this embodiment,step 305 follows step 304 and adds the current volume along with themanagement options retrieved in step 304 to the set of volumesdesignated as being managed by the management software. After the newstep 305, the process continues with step 310. In this case, the loop ofsteps 320-324 is also modified to remove from the management softwarethe volumes that have not been added by the new step 305. The CodeExample section presented below includes one implementation of thisembodiment.

FIG. 4A is a flow chart of a process for retrieving volume managementoptions for the process of FIG. 3 by searching a control file by a firstfit approach, in accordance with embodiments of the present invention.The first fit approach of FIG. 4A begins at step 400, and is one exampleof a retrieval technique utilized by step 304 (see FIG. 3). Step 402obtains volume information that is associated with the current volume asindicated by the loop starting at step 304 (see FIG. 3). The volumeinformation is collected by the data collection tool utilized in step302 of FIG. 3. The volume information includes, for instance, thecurrent volume's serial number, capacity, and hardware details.

In step 404, the volume information obtained in step 402 is compared tothe first record in control file 216 (see FIG. 2). For example, thecurrent volume's serial number is compared to the identification patternincluded in the first record of control file 216 (see FIG. 2). Eachrecord of the control file includes an identification pattern, which iseither a specific identifier that identifies a specific volume or ageneric pattern or mask that identifies a group of volumes. Each recordof the control file also includes a set of management options associatedwith the specific identifier or generic pattern. The patterns and theirassociated volume management options are determined, for instance, byconsidering the type of hardware on which the volume exists. Forexample, a user may determine that management options for expensive,newer hardware are different from the management options for cheaper,older hardware.

If the serial number of the current volume does not match theidentification pattern of the first record of control file 216 (see FIG.2), inquiry step 406 determines if there are other records in controlfile 216 (see FIG. 2) that have not yet been compared to the volumeinformation. If step 406 determines that there are additional records inthe control file, step 408 compares the volume serial number of thecurrent volume to the specific identifier or generic pattern included inthe next record in the control file. If step 408 determines that thereis no match between the identification pattern of the next record andthe volume information, then the process repeats starting at step 406.Otherwise, there is a match between the identifier of the next recordand the volume information, and the management options included in thenext record are returned in step 410 to the process of FIG. 3, and thesearch process of FIG. 4A ends at step 412.

Returning to step 404, if the first record in the control file matchesthe volume information, step 410 returns the management options includedin the matched first record of control file 216 (see FIG. 2) to theprocess of FIG. 3, and the search process of FIG. 4A ends at step 412.

Returning to step 406, if no additional records exist in control file216 (see FIG. 2) (e.g., all records in the control file have beencompared to the volume information obtained in step 402 and no match hasbeen found in steps 404 or 408), then an error is returned in step 414and the search process of FIG. 4A ends at step 412.

FIG. 4B is a flow chart of a process for retrieving volume managementoptions for the process of FIG. 3 by searching a control file by a bestfit approach, in accordance with embodiments of the present invention.The best fit approach of FIG. 4B begins at step 420, and is one exampleof a retrieval technique utilized by step 304 (see FIG. 3). Step 422obtains volume information that is associated with the current volume ofthe loop starting at step 304 (see FIG. 3). Again, the volumeinformation is obtained by the data collection tool utilized in step 302of FIG. 3, and includes, for instance, the volume's serial number,capacity, and hardware details.

In step 424, the volume information is compared to the first record incontrol file 216 (see FIG. 2). Similar to the comparison in steps 404and 408 of FIG. 4A, step 424 compares, for example, the volume serialnumber to an identification pattern (i.e., a specific identifier or ageneric pattern or mask) of a plurality of identification patternsincluded in control file 216 (see FIG. 2), in which each identificationpattern is associated with a specific set of volume management options.The particular patterns and their associated volume management optionsare determined, for instance, by considering the type of hardware onwhich the volume exists.

Step 424 also determines a rating for the fit of the first record to thevolume information. As one example of a rating technique, asix-character volume serial number included in the volume information iscompared in character-by-character order to six-character genericpatterns in the control file in which a “%” symbol is a catchall symbolthat represents any character. In this example, two types of matches arepossible: an exact match (e.g., “A” in the volume serial number comparedto “A” in the generic pattern) and a generic match (e.g., “C” in thevolume serial number compared to a “%” symbol in the generic pattern).The total rating is determined by one point value being assigned to eachexact match and another point value being assigned to each genericmatch. For this example, the total rating is determined by scoring twopoints for each exact match, one point for each generic match, and zeropoints are scored for a mismatch. For instance, a volume serial ofABC123 compared to AD%%%3 would be compared character-by-character, inleft to right order, for a score of 2+0+1+1+1+2, or a total score of 7.That is, A compared to A is an exact match and is assigned a score of 2;B compared to D is a mismatch that is assigned a score of 0; C comparedto % is a generic match that is assigned a score of 1; 1 compared to %scores 1 for a generic match; 2 compared to % scores 1 for a genericmatch; and 3 compared to 3 scores 2 for an exact match.

As another example of a rating technique that can be utilized in step424, a weighting system can be used for predefined character positions.For instance, the scoring system of the previous example is used, butthe scores for the first three characters are weighted by a factor oftwo. For a comparison of the ABC123 serial number to the AD%%%3 patternin the control file, this weighted technique yields a score of2×2+0×2+1×2+1+1+2, or 4+0+2+1+1+2, or a total score of 10.

Step 426 determines if additional records are included in control file216 (see FIG. 2) which have not yet been compared to the volumeinformation. If step 426 determines that additional records are includedin the control file, then step 428 compares the volume information tothe next record of the control file and a rating for the fit of the nextrecord to the volume information is determined. The comparison andrating determination of step 428 uses the same comparison and ratingtechniques used in step 424. Following step 428, the process loops backto step 426. As the process repeats through this loop, a plurality ofratings is determined. The ratings determined by steps 424 and 428 areexamined to determine which rating meets a predetermined criteria (e.g.,the highest score) that labels the rating as the best rating. The bestrating indicates the best fit between the volume information and arecord of the control file. If step 426 determines that no additionalrecords exist in the control file, then the management options includedin the control file record for which the best rating was determined isreturned in step 430 to the process of FIG. 3, and the search process ofFIG. 4B ends at step 432.

In the event that the best rating is associated with a plurality ofrecords of the control file, step 430 consistently selects one record ofthe plurality of records according to a predetermined selection criteria(e.g., selects the record that is listed in the control file last amongthe plurality of records that have the highest rating).

FIG. 5 is a block diagram of a computing system included in the systemof FIG. 1, in accordance with embodiments of the present invention.Server computing unit 500 may be implemented as computing 202 (see FIG.2). Server computing unit 500 generally comprises a central processingunit (CPU) 502, a memory 504, an input/output (I/O) interface 506, a bus508, I/O devices 510 and a storage unit 512. CPU 502 performscomputation and control functions of computing unit 500. CPU 502 maycomprise a single processing unit, or be distributed across one or moreprocessing units in one or more locations (e.g., on a client andserver). Memory 504 may comprise any known type of data storage media,including magnetic media, optical media, random access memory (RAM),read-only memory (ROM), a data cache, a data object, etc. Storage unit512 is, for example, a magnetic disk drive or an optical disk drive.Moreover, similar to CPU 502, memory 504 may reside at a single physicallocation, comprising one or more types of data storage, or bedistributed across a plurality of physical systems in various forms.Further, memory 504 can include data distributed across, for example, aLAN, WAN or storage area network (SAN) (not shown).

I/O interface 506 comprises any system for exchanging information to orfrom an external source. I/O devices 510 comprise any known type ofexternal device, including a display monitor, keyboard, mouse, printer,speakers, handheld device, printer, facsimile, etc. Bus 508 provides acommunication link between each of the components in computing unit 500,and may comprise any type of transmission link, including electrical,optical, wireless, etc.

I/O interface 506 also allows computing unit 500 to store and retrieveinformation (e.g., program instructions or data) from an auxiliarystorage device, such as a non-volatile storage device (e.g., a CD-ROMdrive which receives a CD-ROM disk) (not shown). Computing unit 500 canstore and retrieve information from other auxiliary storage devices (notshown), which can include a direct assess storage device (DASD) (e.g.,hard disk or floppy diskette), a magneto-optical disk drive or a typedrive.

Memory 504 includes computer program code comprising a volumesynchronization system 514 that synchronizes direct access storagevolumes managed by storage management software (e.g., HSM 214 of FIG. 2)with direct access storage volumes available to a computer system (e.g.,system 202 of FIG. 2). Further, memory 504 may include other systems notshown in FIG. 5, such as an operating system (e.g., Linux) that runs onCPU 502 and provides control of various components within and/orconnected to computing unit 500.

The invention can take the form of an entirely hardware embodiment, anentirely software embodiment or an embodiment containing both hardwareand software elements. In a preferred embodiment, the invention isimplemented in software, which includes but is not limited to firmware,resident software, microcode, etc.

Furthermore, the invention can take the form of a computer programproduct accessible from a computer-usable or computer-readable storagemedium providing program code 514 for use by or in connection with acomputing unit 500 or any instruction execution system to provide andfacilitate the capabilities of the present invention. For the purposesof this description, a computer-usable or computer-readable storagemedium can be any apparatus than can contain or store the program foruse by or in connection with the instruction execution system, apparatusor device.

The medium can be an electronic, magnetic, optical, electromagnetic, orsemiconductor system (or apparatus or device). Examples of a computerreadable storage medium include a semiconductor or solid state memory,magnetic tape, a removable computer diskette, RAM 504, ROM, a rigidmagnetic disk and an optical disk. Current examples of optical disksinclude compact disk-read-only memory (CD-ROM), compact disk-read/write(CD-R/W) and DVD.

A computing unit 500 suitable for storing and/or executing program code514 include at least one processor 502 coupled directly or indirectly tomemory elements 504 through a system bus 508. The memory elements caninclude local memory employed during actual execution of the programcode, bulk storage, and cache memories which provide temporary storageof at least some program code in order to reduce the number of timescode must be retrieved from bulk storage during execution.

Furthermore, the present invention discloses a method for deploying orintegrating computing infrastructure, comprising integratingcomputer-readable code into computer system 200 (see FIG. 2), whereinthe code in combination with computer system 200 (see FIG. 2) is capableof synchronizing direct access storage volumes managed by storagemanagement software with direct access storage volumes available to acomputer system. The disclosed method for deploying or integratingcomputing infrastructure with the capabilities described herein can beoffered as a service on a subscription service.

The flow diagrams depicted herein are provided by way of example. Theremay be variations to these diagrams or the steps (or operations)described herein without departing from the spirit of the invention. Forinstance, in certain cases, the steps may be performed in differingorder, or steps may be added, deleted or modified. All of thesevariations are considered a part of the present invention as recited inthe appended claims.

While embodiments of the present invention have been described hereinfor purposes of illustration, many modifications and changes will becomeapparent to those skilled in the art. Accordingly, the appended claimsare intended to encompass all such modifications and changes as fallwithin the true spirit and scope of this invention.

CODE EXAMPLE

The following REXX code is one example of an implementation of portionsof the synchronization process of FIG. 3. Comments are included inbetween the /* and */ indicators. A line that includes /* . . . */indicates that one or more lines of code are not being shown to allowthe code example to focus on the major steps of FIG. 3, and to avoidrepetitiveness.

/* REXX */ /* Version 1.3.1 */ /* */ /* Dynamically adds, updates, andremoves volumes in management */ /* software to synchronize the set ofvolumes known to management */ /* software to the set of volumesavailable to the computing system. */ /* */ /* Uses a DCollect as asource of all volumes */ /* */ /*Constants */ /* All dcol positioninclude the */ /* extra print character */ C.DCOL_TYPE = 5 /* - Recordtype */ /* ‘V’ type */ C.DCOL_V_VOLSER = 25 /* - Volser */ C.DCOL_V_UNIT= 69 /* - Device type i.e., 3390 */ C.DCOL_V_SG = 83 /* - Storage group*/ /*Global variables */ G.volparm.0 = 0 /* Reference to volume masks */G.sysplex_name = ZLRXVAR(SYSPLXNM) G.sysplex_csid.0 = 0 G.RetCode = 0G.update = NO G.userID = ‘DASDADM’ G.vols.0 = 0 /* List of volumes addedto HSM */ /*The Code */ PARSE UPPER ARG G.update /* Find the systems inthe sysplex (must be hard coded) */ /* Store it in G.sysplex_csid. stem.*/ /*. . .*/ SAY “* SYSTEM INFO” SAY “* System CSID:” G.sysplex_csid.1IF G.sysplex_csid.0 = 1 THEN SAY “* Monoplex name: ”G.sysplex_name ELSESAY “* Sysplex name: ”G.sysplex_name /*. . .*/ CALL OpenVolumeParmTable/* Reads the management options from the */ /* control file for uselater. */ /* See Step 304 of FIG. 3. */ CALL AddVolumes CALLDeleteVolumes EXIT 0 /* Creates the CLI command to add/update any volumethat matches the */ /* line. The command is prepared so it can be usedlater, though it */ /* may never be referenced. */ /* ‘dat’ is therecord from the config file that matches the volume. */ /* ‘line’ is theline number of the records (for error reporting) */ /* */ BuildLine:PROCEDURE ARG dat, line SELECT /*. . .*/ WHEN SUBSTR(dat,12,1) = ‘M’THEN /* Migration volume */ DO str=“MIGRATION(” IF SUBSTR(dat,14,1) =‘Y’ THEN /* Autodump it */  str=str ||“AD(“STRIP(SUBSTR(dat,34,47))”) ”ELSE str=str ||“NOAD ” IF SUBSTR(dat,16,1) = ‘Y’ THEN /* Drain it */ str=str ||“DRAIN ” ELSE str=str ||“NODRAIN ” /*. . .*/val=SUBSTR(dat,28,2) IF val=“ ” THEN str=str||“)” ELSE  str=str||“)THRESHOLD(”val“)” END WHEN SUBSTR(dat,12,1) = ‘P’ THEN /* Primary volume*/ DO str=“PRIMARY(” IF SUBSTR(dat,14,1) = ‘Y’ THEN /* Autodump */ str=str ||“AD(”STRIP(SUBSTR(dat,34,47))“) ” ELSE str=str ||“NOAD ” IFSUBSTR(dat,16,1) = ‘Y’ THEN /* Autobackup */  str=str||“AB ” ELSEstr=str||“NOAB ” /*. . .*/ END OTHERWISE DO SAY“************************************************************” SAY “*Illegal ”Volume Type“ character encountered on line ”line SAY “* ofDD(VOLTABLE)” SAY “* Character found is ‘ ”SUBSTR(dat,12,1)“ ‘ ” SAY “*Processing terminated” SAY “*” SAY “* Return code = 8” EXIT 8 END ENDRETURN str /* */ /* AddVolumes: Automatically adds to managementsoftware volumes */ /* which are available to the system. Automaticallyupdates */ /* management options in management software. */ /*Implements steps 308 & 314 of FIG. 3. */ /* */ AddVolumes: PROCEDUREEXPOSE G. C. “EXECIO * DISKR DCOL(STEM dcol. FINIS)” DO c = 1 to dcol.0IF SUBSTR(dcol.c,C.DCOL_TYPE,1) = “V” THEN IFSUBSTR(dcol.c,C.DCOL_V_SG,1) = “ ” THEN DO vol =SUBSTR(dcol.c,C.DCOL_V_VOLSER,6) unit = SUBSTR(dcol.c,C.DCOL_V_UNIT,4)ent = FindMask(vol) IF ent > 0 THEN DO cmd = “HSEND WAIT ADDVOL “vol”UNIT(”unit“) ” cmd =cmd||SUBSTR(G.volparm.ent,8,LENGTH(G.volparm.ent)-7) /* attaches the CLIcreated in BuildLine */ IF G.update = UPDATEHSM THEN DO ADDRESS TSO cmdIF RC = 0 THEN SAY vol“ added to HSM.” ELSE SAY “hsend command failed!”END ELSE SAY cmd d=G.vols.0+1 /* Store the volume that was just added tobe */ G.vols.d=vol /* used later to determine what volumes should */G.vols.0=d /* be deleted by DeleteVolumes */ END END END RETURN /* */ /*FindMask: */ /* Using the first fit approach, finds the first mask thatmatches */ /* the volser and returns the array index. */ /* ImplementsStep 304 of FIG. 3. */ /* */ FindMask: PROCEDURE EXPOSE G. ARG vol DO v= 1 to G.volparm.0 DO c = 1 to 6 char = SUBSTR(G.volparm.v,c,1) IF char

= ‘.’ THEN IF SUBSTR(vol,c,1)

= char THEN c = 8 END IF c < 8 THEN DO SELECT /*. . .*/ WHENSUBSTR(G.volparm.v,7,1) = “−” THEN DO SAY vol“ ignored.” RETURN 0 ENDWHEN SUBSTR(G.volparm.v,7,1)

= “Y” THEN SAY “NON-GSD volume (”vol“) found!” WHEN LENGTH(G.volparm.v)= 7 THEN DO SAY vol“ ignored. Backup/Dump volumes not supported” RETURN0 END OTHERWISE NOP END RETURN v END END RETURN 0 /* */ /*DeleteVolumes: Automatically removes volumes from management */ /*software. The removed volumes are volumes that are no longer */ /*available to the system. Implements Step 322 of FIG. 3. */ /* */DeleteVolumes: PROCEDURE EXPOSE G. C. /* Cleanup primary volumes */dsname=G.userID“.HSMADVOL.PVOL” address tso “del ‘”dsname“’” address tso“hsend wait list pvol ods(‘”dsname“’)” “alloc dd(pvol) da(‘”dsname“’)shr” “execio * diskr pvol(stem pvol. finis) ” DO c = 1 to pvol.0 vol =SUBSTR(pvol.c,2,6) SELECT /*. . .*/ WHEN SUBSTR(pvol.c,18,5)=“P SMS”THEN NOP /* Ignore SMS volume */ OTHERWISE /* First step, make surevolume is not one of */ DO /* the volumes just added by AddVolumes */ IFJustAdded(vol) = “NO” THEN DO /* Volume was not just added by AddVolumes*/ cmd = “HSEND DELVOL “vol” PRIMARY” IF G.update = UPDATEHSM THEN DOADDRESS TSO cmd IF RC = 0 THEN SAY vol“ deleted from HSM.” ELSE SAY“hsend command failed!” END ELSE SAY cmd END END END END /* CleanupMigration Level 1 (ML1) volumes */ dsname=G.userID“.HSMADVOL.MVOL”ADDRESS TSO “DEL ‘ “dsname” ’ ” ADDRESS TSO “HSEND WAIT LIST MVOL ML1ODS(‘ ”G.userID”.HSMADVOL.MVOL’)” “ALLOC DD(MVOL) DA(‘ “dsname” ’) SHR”“EXECIO * DISKR MVOL(STEM mvol. FINIS) ” DO c = 1 to mvol.0 vol =SUBSTR(mvol.c,2,6) SELECT WHEN vol = “- DFSM”  THEN NOP WHEN vol = “ ”   THEN NOP WHEN vol = “VOLSER” THEN NOP WHEN vol = “ ----- ”    THENNOP OTHERWISE /* First step, make sure volume is not one of */ DO /* thevolumes just added by AddVolumes */ IF JustAdded(vol) = “NO” THEN DO  /*Volume was not just added by AddVolumes */ cmd = “HSEND DELVOL “vol”MIGRATION(PURGE)” IF G.update = UPDATEHSM THEN DO ADDRESS TSO cmd IF RC= 0 THEN SAY vol“ deleted from HSM.” ELSE SAY “hsend command failed!”END ELSE SAY cmd END END END END RETURN Just Added: PROCEDURE EXPOSE G.ARG vol DO c = 1 to G.vols.0 IF vol = G.vols.c THEN RETURN YES ENDRETURN NO

1. A system for synchronizing direct access storage volumes managed bystorage management software with direct access storage volumes availableto a computer system, comprising: means for identifying a first set ofone or more direct access storage volumes, said first set physicallyconnected to and available to said computer system, said identifyingproviding an identifier of a direct access storage volume of said firstset; means for matching said identifier with an identification patternincluded in a record of one or more records residing in a databaseaccessible by said computer system, said identification patternidentifying said direct access storage volume directly or a group ofdirect access storage volumes including said direct access storagevolume; means for retrieving from said record, responsive to saidmatching, a plurality of management options capable of facilitating amanagement of said direct access storage volume by said storagemanagement software, wherein said direct access storage volume is notdesignated as being managed by said storage management software; andmeans for automatically adding said direct access storage volume to asecond set of one or more direct access storage volumes, said second setdesignated as being managed by said storage management software, whereinsaid means for adding comprises: means for designating said directaccess storage volume as being managed by said storage managementsoftware, and means for providing said plurality of management optionsto said storage management software, wherein said storage managementsoftware associates said plurality of management options with saiddirect access storage volume.
 2. The system of claim 1, furthercomprising: means for obtaining a second identifier of a second directaccess storage volume of said first set, wherein said second directaccess storage volume is managed by said storage management software;means for matching said second identifier with a second identificationpattern included in a second record of said one or more records, saidsecond identification pattern identifying said second direct accessstorage volume directly or a second group of direct access storagevolumes including said direct access storage volume; means forretrieving from said second record, responsive to said matching saidsecond identifier, a first set of management options capable offacilitating management of said second direct access storage volume bysaid storage management software; means for retrieving from said storagemanagement software a second set of management options associated withsaid second direct access storage volume by said storage managementsoftware, wherein said second set is different from said first set; andmeans for automatically updating said second set of management optionsto be identical to said first set of management options.
 3. The systemof claim 2, further comprising: means for repeating said adding for eachdirect access storage volume of said first set not designated as beingmanaged by said storage management software until said one or moredirect access storage volumes of said first set are designated as beingmanaged by said storage management software; means for determining asecond direct access storage volume of said second set is not in saidfirst set; and means for automatically removing, responsive to saiddetermining said second direct access storage volume, said second directaccess storage volume from said second set, wherein said removingcomprises designating said second direct access storage volume as notbeing managed by said storage management software.
 4. The system ofclaim 1, wherein said plurality of management options defines at leastone of: an automatic migration of data residing on said direct accessstorage volume to a migration volume of a specified category, whereinsaid migration occurs in response to a occupancy rate of said directaccess storage volume being at least a first specified threshold rate,said data being at least a first specified age, or a first specifiedtime elapsing since a reference of said data, an expiration of saiddata, wherein said expiration occurs in response to said occupancy ratebeing at least a second specified threshold rate, said data being atleast a second specified age, or a second specified time elapsing sincea reference of said data an automatic backup of said data to a specifiedcategory of a backup device, wherein said backup occurs in response tosaid data being at least a third specified age, or a third specifiedtime elapsing since a reference of said data, an automatic volume dumpof allocated space on said direct access storage volume to a specifieddump volume based on a specified frequency, and an automatic recall ofsaid data from a migration volume to said direct access storage volume.5. The system of claim 1, wherein said means for identifying utilizes asoftware facility to collect one or more unique volume serial numbersassociated with said one or more direct access storage volumes of saidfirst set in a one-to-one correspondence, wherein a volume serial numberof said one or more volume serial numbers is said identifier.
 6. Thesystem of claim 1, wherein said storage management software is DataFacility System Managed Storage Hierarchical Storage Manager (DFSMShsm).7. A computer program product comprising a computer-usable storagemedium including computer-usable program code stored on computerreadable storage medium for synchronizing direct access storage volumesmanaged by storage management software with direct access storagevolumes available to a computer system, the said computer programproduct stored on computer readable storage medium, including:computer-usable code for identifying a first set of one or more directaccess storage volumes, said first set physically connected to andavailable to said computer system, said identifying providing anidentifier of a direct access storage volume of said first set;computer-usable code for matching said identifier with an identificationpattern included in a record of one or more records residing in adatabase accessible by said computer system, said identification patternidentifying said direct access storage volume directly or a group ofdirect access storage volumes including said direct access storagevolume; computer-usable code for retrieving from said record, responsiveto said matching, a plurality of management options capable offacilitating a management of said direct access storage volume by saidstorage management software, wherein said direct access storage volumeis not designated as being managed by said storage management software;and computer-usable code for automatically adding said direct accessstorage volume to a second set of one or more direct access storagevolumes, said second set designated as being managed by said storagemanagement software, wherein said computer-usable code for addingcomprises: computer-usable code for designating said direct accessstorage volume as being managed by said storage management software, andcomputer-usable code for providing said plurality of management optionsto said storage management software, wherein said storage managementsoftware associates said plurality of management options with saiddirect access storage volume.
 8. The program product of claim 7, furthercomprising: computer-usable code for obtaining a second identifier of asecond direct access storage volume of said first set, wherein saidsecond direct access storage volume is managed by said storagemanagement software; computer-usable code for matching said secondidentifier with a second identification pattern included in a secondrecord of said one or more records, said second identification patternidentifying said second direct access storage volume directly or asecond group of direct access storage volumes including said directaccess storage volume; computer-usable code for retrieving from saidsecond record, responsive to said matching said second identifier, afirst set of management options capable of facilitating management ofsaid second direct access storage volume by said storage managementsoftware; computer-usable code for retrieving from said storagemanagement software a second set of management options associated withsaid second direct access storage volume by said storage managementsoftware, wherein said second set is different from said first set; andcomputer-usable code for automatically updating said second set ofmanagement options to be identical to said first set of managementoptions.
 9. The program product of claim 8, further comprising:computer-usable code for repeating said adding for each direct accessstorage volume of said first set not designated as being managed by saidstorage management software until said one or more direct access storagevolumes of said first set are designated as being managed by saidstorage management software; computer-usable code for determining asecond direct access storage volume of said second set is not in saidfirst set; and computer-usable code for automatically removing,responsive to said determining said second direct access storage volume,said second direct access storage volume from said second set, whereinsaid removing comprises designating said second direct access storagevolume as not being managed by said storage management software.
 10. Theprogram product of claim 7, wherein said plurality of management optionsdefines at least one of: an automatic migration of data residing on saiddirect access storage volume to a migration volume of a specifiedcategory, wherein said migration occurs in response to a occupancy rateof said direct access storage volume being at least a first specifiedthreshold rate, said data being at least a first specified age, or afirst specified time elapsing since a reference of said data, anexpiration of said data, wherein said expiration occurs in response tosaid occupancy rate being at least a second specified threshold rate,said data being at least a second specified age, or a second specifiedtime elapsing since a reference of said data an automatic backup of saiddata to a specified category of a backup device, wherein said backupoccurs in response to said data being at least a third specified age, ora third specified time elapsing since a reference of said data, anautomatic volume dump of allocated space on said direct access storagevolume to a specified dump volume based on a specified frequency, and anautomatic recall of said data from a migration volume to said directaccess storage volume.